DNS Internal/External Views - No servers could be reached

lazydog · 07-21-2015, 12:20 PM

Quote:

Originally Posted by dansdionne

Yes, I can ping myself

Finally, some progress.

This is good news

Quote:

I have disabled all port forwarding on both the modem and the router. The only thing I hadn't backed out is static IP assignments for my server and pc on the router. Let me try.... It worked! I removed the static IP assignment for the server and now I can ping 8.8.8.8, google.com, and anything else. Any ideas why that might be causing a problem?

Maybe, look at what ip address your system now has with

Code:

ifconfig
route -n

Quote:

Now I can finally start debugging my split view DNS. It doesn't resolve my FQDN internally yet, but I don't have any specific questions about it yet. When I do, I will post here! If I figure it out on my own, I will be sure to update the thread with my solution as well.

Thanks for all of your help!

-Dan

You are welcome.

berndbausch · 07-21-2015, 05:54 PM

This is the start of mine. My domain is home.

Code:

; modeled after https://wiki.archlinux.org/index.php/Bind
;
$TTL    1d

@       IN  SOA ns01.home. mail.home. (
 2015070801 ; serial #
 5d      ; refresh interval
 15m     ; retry if master unavail
 1w      ; records getting stale
 1h      ; TTL for negative results
 )

 IN  NS  ns01
 IN  NS  ns02
ns01 IN  A   192.168.1.16
ns02 IN  A   192.168.1.1 ; lame delegation

5220 IN  A   192.168.1.17 ; 60:eb:60:5b:45:28 mini-Probook
5220-wl     IN  A   192.168.1.15 ; 00:27:10:C5:F9:B4 mini-Probook WL
.......

I am far from being an expert. The Archlinux wiki page may be useful.

dansdionne · 07-27-2015, 05:29 PM

Quote:

Originally Posted by dansdionne

I am at work, so I can't test this, but should my SOA read "ns.myftp.org" instead of "ns.hostname.myftp.org", with A records:

Code:

ns          IN  A      192.168.1.140
hostname    IN  A      192.168.1.140

I don't need to resolve any other hosts at myftp.org.

I just want to follow up on this post and let people know that once I got my connection working again, the above quote is the only change I had to make to my internal/external split zone DNS. I can now successfully resolve hostname.myftp.org from my internal network, which wasn't working for me for a long time. I had tried a number of other things before stumbling on this fairly simple solution. I hope other people will find this useful.

Thanks again for all of your help.

-Dan