Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Wed, 4 Aug 2004 18:42:55 UT "dan moylan" <jdm at moylan.info> wrote: > > miah writes: > > When you do reverse lookups it allways goes backwards by > > ip, so if the ip is 192.168.1.1 it will lookup > > 1.1.168.192 go read dns & bind. > > well, ok. but how come it came out forward for one host > and backward for the other? that's inconsistant and not > going to be answered by reading dns & bind. > > and anyway, the other name servers i used gave the right > answer for both hosts. It is possible that the original DNS entry was incorrect and later corrected by affordable.com, but it had not yet propagated you your router. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.blu.org/pipermail/discuss/attachments/20040804/dce70d69/attachment.sig>
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |