ATTN: Ubuntu 8.04 Users

Quote:

---

Originally Posted by ScottChapman

I am following the instructions in the Wiki.

I modified the named.conf.options file and the resolve.conf

restarted bind9

But I cannot resolve names. ping google.com doesn't resolve.

I know I put my router in as the forwarder (which is what all my machines on my home network use), and put the private IP address of my box in as the nameserver (the private IP is the IP my machine is known as on my local network).

Any ideas?

---

First question: is your dns actually functioning? If you ping <yourhostname> does it resolve to itself and ping? Same idea with nslookup <yourhostname> --does it resolve?

Instead of using your router IP as a forwarder, try the DNS server IP that your router uses.

Im guessing your router can provide DNS server (via DHCP) information to clients, but not DNS services.

at a command prompt:

ipconfig /all

and see what nameservers are listed on any of the client machines inside your network.

Hi everyone,

I have installed Ubuntu 8.04 LTS on a server machine to install Zimbra on, I have followed the The Perfect Server - Ubuntu Hardy Heron and also followed the Instructions as per dwmtractor post referring people to the Wiki listed below.
Ubuntu 8.04 LTS Server (Hardy Heron) Install Guide - Zimbra :: Wiki

I am having a problem though I have set up the DNS as per the instructions in the wiki and can successfully nslookup hosts like goole.com or yahoo.com however when I try to nslookup my host xyz.com.au for example I get the following error

root@mail:~# nslookup xyz.com.au
Server: 10.0.0.9
Address: 10.0.0.9#53

** server can't find xyz.com.au.xyz.com.au: SERVFAIL

Any ideas why the domain name is being resolved twice ?

The server and address are correct and I can see why it cant find the host, cause the host name is listed twice in the request.

Any ideas ?????

Thanks
ikhan42

Guys ignore my last post I figured it out :)

Quote:

---

Originally Posted by ikhan42

Guys ignore my last post I figured it out :)

---

Actually, instead of ignoring it, might you post what happened so we all can benefit from another "gotcha" to watch out for? Hosts file? Syntax in named.conf? Inquiring minds would love to know. . . ;)

I have this exact same problem without a solution. Could the solution be posted please.

Quote:

---

Originally Posted by dlader

I have this exact same problem without a solution. Could the solution be posted please.

---

I had an issue like that once, and I believe the problem was created because I made DNS changes but did not increment the serial number in the zone file, therefore DNS was not updating as it should to the rest of the world cuz it thought there was no change. What was actually happening was DNS was working of the "old" settings in the public realm, and the new settings when referencing internally.

Thank you for the reply but I still have the same problem. I can get the proper results for IPs outside of my network, but I get the same error for everything inside my network.

Sorry I left the forum due to attitude problems that I had with one of the employees. I worked all the stuff out then I dumped the product for one that had a friendlier community. I wont help this product when the staff arent willing. Will use my time in communities that are willing to help and make a better, friendlier product.

This may be the wrong attitude and isnt the way I am normally but one of the employees rubbed me up the wrong way bad enuff for me to turn my back on the product.

ikhan42