This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Matching forward and reverse DNS for DSL pool addresses
- Previous message (by thread): [dns-wg] Matching forward and reverse DNS for DSL pool addresses
- Next message (by thread): [dns-wg] Announcement: Policy Development Process in RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
brian.wilkinson at bt.com
brian.wilkinson at bt.com
Wed Dec 1 14:24:47 CET 2004
ok - Thanks to all that replied. We already provide matching forward and reverse - I just wanted to verify that it was definitly required as I am currently reviewing our DNS management processes. Regards Brian -----Original Message----- From: Jim Reid [mailto:jim at rfc1035.com] Sent: Wednesday, December 01, 2004 12:48 PM To: Wilkinson,BJ,Brian,XJG11 R Cc: dns-wg at ripe.net Subject: Re: [dns-wg] Matching forward and reverse DNS for DSL pool addresses >>>>> "brian" == <brian.wilkinson at bt.com> writes: brian> Can anyone confirm whether DSL (and dial) providers are brian> required to provide matching forward and reverse DNS for brian> the address pools or is a wildcard in the reverse zones brian> sufficient? There's no requirement. Though your customers might appreciate it if reverse lookups worked for the IP addresses. Sometimes applications will make life difficult for hosts that don't have working reverse DNS. For instance a client that initiates an SMTP connection may be considered a spam source if there's no sensible answer to a reverse lookup of the client's address. And as Peter has said, wildcards are probably not a good idea for this sort of thing. It could also break when the application does a forwward lookup of the name returned by a reverse lookup. The BSD r- protocols -- which I hope nobody uses any more -- do this to decide if the client is who they claim to be and therefore determin if the client is trusted or not.
- Previous message (by thread): [dns-wg] Matching forward and reverse DNS for DSL pool addresses
- Next message (by thread): [dns-wg] Announcement: Policy Development Process in RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]