View Full Version : [ubuntu] Web Server DNS Not Resolving

November 25th, 2010, 09:19 AM
I've installed a web server on my server, and it works great; however, DNS will not resolve for any domains I add to the web server.

For example, I've created custom ns records at GoDaddy.com to point

ns1.mydomain.com to
ns2.mydomain.com to

Thus, my clients should set their name servers to ns1.mydomain.com and ns2.mydomain.com and have them be routed to is my server's external IP
192.168.x.119 is my server's local IP address

These entries are not resolving even though they have been setup properly in the GoDaddy control panel.

Connecting via direct IP does resolve however:

Ports are all unblocked including 53.

Here's how my network is setup:

Internet Settings

Gateway MAC Address 00:22:2D:96:68:FE
WAN MAC Address 00:22:2D:96:69:02
WAN DHCP Subnet Mask
WAN DHCP Default Gateway
WAN Internet IP Address
DNS (primary)
DNS (secondary)
DHCP Time Remaining 68h:02m:55s
Date NOV-25-2010
Static IP Block (
Local Settings
Gateway IP Address
Subnet Mask
DHCP Server Enabled
IP Range (start)
IP Range (end)
Router 1 Settings:

Local Settings
Gateway IP Address
Subnet Mask
DHCP Server Enabled
IP Range (start)
IP Range (end)

Router 2 Settings:

IP Address : 192.168.x.43
Subnet Mask :
Default Gateway :
Primary DNS Server :
Secondary DNS Server :

Ports are forwarded for (Router 2) and then ports are forwarded on (Router 2) to the server's IP address of 192.168.x.119

The following files contain the below entries:



dhclient.conf under dhcp3:

#prepend domain-name-servers
prepend domain-name-servers
prepend domain-name-servers
prepend domain-name-servers

The DNS Template on the server is:

$TTL 86400
@ IN SOA ns1.{domainname}. {dnsemail} (
{serial} ; Serial
10800 ; Refresh
1200 ; Retry
86400 ; Expire
86400 ) ; Minimum
ns1.{domainname}. IN NS ns1.{domainname}.
ns2.{domainname}. IN NS ns2.{domainname}.
ns.{domainname}. IN A {dnsip}
ns1.{domainname}. IN A {dnsip}
ns2.{domainname}. IN A {dnsip}
dns.{domainname}. IN A {dnsip}
dns1.{domainname}. IN A {dnsip}
dns2.{domainname}. IN A {dnsip}
{domainname}. IN A {webip}
mail.{domainname}. IN A {mailip}
smtp.{domainname}. IN A {webip}
webmail.{domainname}. IN A {webip}
ftp.{domainname}. IN CNAME {domainname}.
www.{domainname}. IN CNAME {domainname}.
{domainname}. IN MX 10 mail.{domainname}.
{domainname}. IN TXT "v=spf1 a mx"
* IN A {webip}
My IP address is:
I set NS1.mydomain.com to resolve to
I set NS2.mydomain.com to resolve to

Any ideas what's wrong? Why won't ns1.mydomain.com resolve for clients or myself?

November 25th, 2010, 09:52 AM
what does

$ ping ns1.mydomain.com

November 25th, 2010, 02:00 PM
You have to be running a nameserver if you point the NS records to that address. Are you running BIND?

There really isn't a good reason to run a nameserver yourself if you're just trying to provide external DNS services. Just point the NS records to the GoDaddy servers and set up the records there.

November 25th, 2010, 05:42 PM
I'm currently at a Windows machine, and here's what it says when I ping:

ping ns1.webehostin.com
Ping request could not find host ns1.webehostin.com. Please check the name and t
ry again.

I have setup the entries at GoDaddy correctly.

Host Summary Entries

ns1.mydomain.com ---
ns2.mydomain.com ---

Adding the entries used to work fine standalone until ICANN changed the rules. Now, the server at must also have the correct DNS entries and be setup for use with that host summary.

Is there anything else network side that I need to setup for DNS? What am I missing?

November 27th, 2010, 09:36 AM

November 27th, 2010, 02:23 PM
You need an A record at GoDaddy that points www.yourdomain.com to your server's IP address.