Re: What is this?
From: Anders (andersajja_at_hotmail.com)
Date: 10/03/05
- Next message: landenmelton_at_gmail.com: "Re: Route all traffic through Netgear FVS318v3 VPN"
- Previous message: Ron Lopshire: "Re: Norton Internet Security 2005"
- In reply to: Moe Trin: "Re: What is this?"
- Next in thread: Moe Trin: "Re: What is this?"
- Reply: Moe Trin: "Re: What is this?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 03 Oct 2005 17:32:53 GMT
Moe Trin wrote:
>
> This fails on a properly set up firewall. If there are no name servers
> meant to be publicly accessible behind the firewall, there is no reason
> to all traffic to port 53 inbound. Where I work, we have three publicly
> accessible DNS servers - one in the DMZ, and two located at our upstream.
> All internal DNS requests go to servers behind the firewall, but as there
> is no reason for external hosts to know internal names, the external DNS
> servers are set to return "generic" answers to requests - so that when a
> request comes in for the name of 192.0.2.2, the answer returned is
> "192.0.2.2.example.com" rather than "file_server.example.com". That
> answer satisfies those who "must" have a "valid" hostname to put into
> their logs - (and if someone does the reverse lookup, and follows it with
> a forward lookup of 192.0.2.2.example.com, they get the 192.0.2.2
> answer), but those answers don't provide useful information about the
> layout of our internal LAN. Creating those zonefiles is trivial - just
> a couple of dumb shell scripts. An external request for a public
> system (such as www.example.com) does return the valid IP address of
> the web server in the DMZ (and a reverse lookup of that IP does
> return the 'www.example.com'), so the public can go there, but no further.
>
> Old guy
Now I have readed the "DNS-HOWTO", and in there was this link to "How to
secure my DNS server"
(http://www.etherboy.com/dns/chrootdns.html) and that will probable
cover secureity issues, but I have not had the time for it rigth now.
But I have "dig" my ISP and that work as it should and also the
localhost (127.0.0.1).
This link did not work (http://www.etherboy.com/dns/chrootdns.html) so
that have I not been able to read up about, maybe it just is down temporary.
Thank You for time taken, and al useful info about DNS and traceroute.
Regards Anders
- Next message: landenmelton_at_gmail.com: "Re: Route all traffic through Netgear FVS318v3 VPN"
- Previous message: Ron Lopshire: "Re: Norton Internet Security 2005"
- In reply to: Moe Trin: "Re: What is this?"
- Next in thread: Moe Trin: "Re: What is this?"
- Reply: Moe Trin: "Re: What is this?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|