Bah, why does this seem to happen at every NANOG conference? Looks like someone has just put in the reverse DNS for the NANOG network IP addresses, but not put in forward DNS. This breaks tcp_wrappers. Can someone fix? Simon -- Simon Lockhart | Tel: +44 (0)1737 839676 Internet Engineering Manager | Fax: +44 (0)1737 839516 BBC Internet Services | Email: Simon.Lockhart@bbc.co.uk Kingswood Warren,Tadworth,Surrey,UK | URL: http://support.bbc.co.uk/
Looks okay to me, eg: [philip@pfs-pc philip]$ dig -x 65.174.251.254 ;; ANSWER SECTION: 254.251.174.65.in-addr.arpa. 86400 IN PTR infra-251-254.nanog23.merit.net. [philip@pfs-pc philip]$ dig infra-251-254.nanog23.merit.net ;; ANSWER SECTION: infra-251-254.nanog23.merit.net. 3600 IN A 65.174.251.254 Was there a particular example you have? philip -- At 00:38 22/10/2001 +0100, Simon Lockhart wrote:
Bah, why does this seem to happen at every NANOG conference?
Looks like someone has just put in the reverse DNS for the NANOG network IP addresses, but not put in forward DNS. This breaks tcp_wrappers.
Can someone fix?
Simon -- Simon Lockhart | Tel: +44 (0)1737 839676 Internet Engineering Manager | Fax: +44 (0)1737 839516 BBC Internet Services | Email: Simon.Lockhart@bbc.co.uk Kingswood Warren,Tadworth,Surrey,UK | URL: http://support.bbc.co.uk/
participants (2)
-
Philip Smith -
Simon Lockhart