Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 5041 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Bind DNS Problems

JustinWoolington

Here is what I'm trying to accomplish. 

I am trying to host my own website with a domain name registered with namecheap.com.

I have a Raspberry Pi with Debian installed on it and bind9 for DNS. I have probably installed deleted and installed it and configured it 5 times now. I feel like I am missing something or am not doing something right. 

I am also behind a SOPHOS UTM firewall and have configured the firewall like so:

I've also tried multiple DNAT & SNAT rules.

After installing and configuring bind on the Pi, I was able to dig and get the proper results. Was able to nslookup and get proper results. I was also able to ping ns1.mydomain.net and get a reply from my public IP which I configured in my zone files. All of which was done from inside the Pi.

Here is the thing. I can't ping outside of the Pi to ns1.mydomain.net, and I also can't do an nslookup either. What's really really weird though is that today when I pinged ns1.mydomain.net from my work PC, I got a reply from my public IP, but I remoted into another PC and tried to ping it, it says could not find host. I even tried to ping inside my home network on my main PC, and it says the same thing, host couldn't be found. 

My public IP is from comcast so it's a dynamic IP, which I intend to update frequently as it changes. And I've done my research on default blocked ports on residential Internet: https://customer.xfinity.com/help-and-support/internet/list-of-blocked-ports/ and none that are blocked should be affecting what I'm trying to accomplish.

Am I missing something?? 



This thread was automatically locked due to age.
  • 0

    Resolved. 

    Possibly a TTL issue or latency. Everything was set up correctly. 

    Refreshed my DNAT rules (turned off and back on) not sure if this is a bug issue..

    I'm able to nslookup and get proper results inside and out of the Pi and home network. I'm also able to dig outside and get proper results.

  • 0

    While not technically mis-configurations, there are several things you can do to clean up what you presented in this thread...

    Your first firewall rule in your first post above may have no effect.  Outbound pinging is regulated on the 'ICMP' tab of 'Firewall', but inbound pings and DNS can only be redirected to the Pi with a NAT rule.  If the NAT rule has automatic firewall rules selected, this rule would be redundant as the automatic rules are applied before manual ones (see #2 in Rulz).

    In no case does "External (Address)" have any effect in the first and third rules.

    For your second post here, check #5 in Rulz.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    Thanks for the reply Bob.

     

    I've reconfigured my NAT rules with the "Automatic firewall rule" unchecked, and have created Firewall rules for them. 

    One my 1st and 3rd rules, I was using the "External (Address)" just for testing. 

Unfiltered HTML