Possible DNS Server Issue?

[gplemos]

I have what seems to be a tricky DNS NT4 issue on my network.

From our LAN we can connect to our webservers websites by name or IP address. These web servers are on the other side of our proxy server with their own public IP addresses.

But people on the internet (outside) cannot connect to our websites by website name. They can however connect to our websites by their IP addresses.

So I'm lead to believe this is definitely a DNS issue.

Here's something I do not understand. If our web servers have their own PUBLIC IP addresses, and people on the internet can not resolve the website names, how can WE on the internal LAN be able to resolve them? EVEN THOUGH THEY ARE ON THE PUBLIC SIDE OF OUR NETWORK? PUBLIC IS PUBLIC. Can this perhaps just be our Proxy server working to get the clients connected over, and because the proxy server has an IP address in the same range it can see the other machines (web servers)? That has me a bit stumped.

Anyway, our DNS server seems to be working fine. I logged in, saw that DNS is operational, and the records are all still there. I can ping the DNS server from another (remote) location, but if I run nslookup for any site that our DNS server is responsible for it tells me it is non existant. However if I run NSLOOKUP from the DNS Server, or any of our servers in the same public IP address range it lists the name and ip address correctly.

Any suggestions, or where else to look?

Thanks!

 

[Zelandakh]

You can connect properly as you have your own DNS with its own entries for your server. What you need to do is query the real DNS on the Internet to check if your entries are all there.

Go to samspade.org and search DNS for your domain. Bet you don't get many entries.

Write down the ones that don't work and ask your ISP to add them to their DNS. Next update everyone outside your LAN can gain access by name.

 

[ITGL72]

Yes we have our own DNS, but its on the other side of the proxy (which can see the external side and internal side) Our DNS servers are on the external side. We do not use our ISP's DNS servers. We use 2 of our own. Our primary DNS server is authoritive for all our domains and the domains are registered with directnic.com

I'll check out that site. Any other suggestions?

 

[gplemos]

I'm thinking there is a conflict somewhere.

For example, 3 of the domains I have on my webservers are:

http://www.esaonline.com

http://www.promise-net.com

http://www.esaconnect.com

http://www.stiesa.com

My name servers are ns.nnlltd.net and ns2.nnlltd.net. My company DOES NOT OWN nnlltd.net (past admin
does)

I have all domain names registered with directnic.com.
My name servers are entered or supposed to be entered on directnic.com as

ns.nnlltd.net
208.60.99.2

and

ns2.nnlltd.net
208.60.99.8

If I go to

http://www.networksolutions.com/cgi-bin/whois/whois

and lookup:

stiesa.com I get:
Domain servers in listed order:
NS.NNLLTD.NET 208.60.99.2
NS2.NNLLTD.NET 208.60.99.8


for promise-net.com I get:
Domain servers in listed order:
NS.NNLLTD.NET 63.167.141.21
NS2.NNLLTD.NET 63.167.141.22


for esaonline.com I get:
Domain servers in listed order:
NS.NNLLTD.NET 63.167.141.21
NS2.NNLLTD.NET 63.167.141.22


for esaconnect.com I get:
Domain servers in listed order:
NS.NNLLTD.NET 208.60.99.2
NS2.CL.BELLSOUTH.NET 205.152.16.8


What the heck? Some point to the 208 address for the NNLLTD.NET and other point to the 63 address.

I am going to have to redo a DNS server, give it another domain name and set it up from scratch and
see what happens perhaps?