asked on

DNS Record or Port Mapping?

All,

I have a web server sitting inside of a production network. This web server, tdxs3, has been assigned an external IP address of 96.2.192.139 which DNS should point to it's internal IP address of 172.30.115.246. When trying to hit it from the outside using tdxs3.dsdk12.net, nothing pops up. Hit the IP however, and it works. (Internally, everything works, of course - nothing to resolve) By the way, the switch routes the external IP to the internal IP. So, I think it's port mapped properly. So I'm fairly certain this is a DNS issue. I've changed the DNS record, incremented the SOA serial and restarted named. (FreeBSD box) But even after 24 hours, I'm getting nothing. (I have two DNS zone masters, one for external, the other for internal)

This is the record for external:

tdxs3 IN A 96.2.192.139

tdxs3 IN CNAME tdxs3.dsdk12.net

And internal:

tdxs3 A 172.30.115.246

Am I missing something really obvious here?

0xSaPx0

Easy test. From externally point your DNS to your external dns. If it resolves its a propagation issue, if it does not resolve it is a DNS record issue.

All you need is a DNS A record which I see you have to get resolution working so my guess is that it is a propagation issue.

If you have home based internet as opposed to business its worth calling your ISP to verify they have no problem with you running a DNS server.

Tim Phillips

Is there a router between the server and the internet? If so you need to either forward the ports for web (port 80, 443) or use one-to-one NAT.

Jcb1974

ASKER

Yeah, I have a switch between the production web server and the outside. The firewall is actually forwarding traffic to the internal IP with a rule. But it isn't resolving. Mayhaps another 24 hours, if it is a propagation issue?

0xSaPx0

If you can get to it via IP, you don't have a problem with firewall rules or NAT/PAT.

This is specifically a DNS issue.

Jcb1974

ASKER

That's precisely what I thought. And it appears the A records I have in DNS are formatted correctly, right? So, I presumed it was DNS. I dropped my TTL to 60, and figured I'd wait 24 hours.

0xSaPx0

Propagation is generally 1 - 48 hours. So its most likely that. However, if you point directly at the DNS server in your DNS Settings, you should be able to resolve the name (all this is external), if so then its simply a waiting game.

ASKER CERTIFIED SOLUTION

gheist

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jcb1974

ASKER

Thanks for the help!