Discussion Locked

wierd DNS problem

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi folks,

the setup:
We have primary internal IP net (10.x.x.x) and a wan (192.168.x.x) We have an internal DNS server, which resolves both internal and internet namelookups for the clients.

the problem:
DNS lookup is not working over the wan connection. I can ping the dns server with success from the wan, but it refuses to answer a dns lookup.

The dns service works perfectly for the clients on the internal net.

I have tested the route tabels, and the are working as exspected.

all other tcp/ip communication over the wan is working.

So what the heck is wrong???
What have I forgotten?

11 replies

by dheupel

Do you have a firewall, or proxy server between your internal network, and the WAN? DNS traffic is transported on IP port 53. Open port 53 on your firewall and proxy server, and your two DNS servers should then be able to send DNS information to each other.

Good Luck.

by thomas

The wan-link is not behind our firewall.
and the router to the wan connection has not been configured to filter any ports, so port 53 is open.

by Former member

Your WAN, at least, must have a valid, public address. THe addresses you mentioned are not public addresses, but private, and cannot be used for internet access. Maybe you forgot to mention the private addresses you are using, starting with the public address of your DNS server.

by strong002

If the FQDN for the 192.168.x.x is not a subset of the 10.x.x.x network it will not function properly. I.E. if the 10.x.x.x network is mycompany.com then the 192.168.x.x would have to be remote.mycompany.com. 192.168.x.x can not be mycompany.com because the DNS server can only resolve names under or below mycompany.com. If 192.168.x.x is also mycompany.com 10.x.x.x and 192.168.x.x are seen as peers and neither will be able to resolve any DNS names outside itself.

by jackieb

Maybe you need to configure an interface on your DNS into each of the two networks, I.E., one network connection using a 10.x.x.x address connected to the 10.x.x.x network and another network interface configured with a 192.168.x.x address connectedto the 192.168.x.x network. If not, I think there may be an option setting on the router to ensable it to pass DNS lookups along to a different network than the one that the DNS machine is on. I can't remember what it is called but I believe it exists. This is independant to the route tables, and is involved in allowing that particular type of packet to propagate to another network. Either answer may work for you. Good luck. JackieB

by mganz_911

If you are using a proxy server and the dns you must add a filter to the winsox proxy so the dns can open port 53 for the dns lookup

This discussion is closed to new replies.