Impact of having loghost defined in DNS...?

Gregory Hicks ghicks at cadence.com
Sun Nov 28 09:40:02 UTC 2004


Greetings:

Not sure if this is "on-topic" or not, but what would you expect the
impact of defining "loghost" to be 127.0.0.1 via DNS...

My db.127.0.0 PTR file already has

1.0.0.127.IN-ADDR.ARPA.         IN  PTR   localhost.

entered, and I don't see how any other name can be added to this when
running under Bind 9.3...

It would be possible to define loghost as

loghost.example.com.    IN A 127.0.0.1
localhost.example.com.  IN A 127.0.0.1

in the main zone file, but I don't see any other way to do it other
than defining the entry in the /etc/hosts file.

Any thoughts on any potential impacts?

Regards,
Gregory Hicks

---------------------------------------------------------------------
Gregory Hicks                           | Principal Systems Engineer
Cadence Design Systems                  | Direct:   408.576.3609
555 River Oaks Pkwy M/S 6B1             | Fax:      408.894.3479
San Jose, CA 95134                      | Internet: ghicks at cadence.com

I am perfectly capable of learning from my mistakes.  I will surely
learn a great deal today.

"A democracy is a sheep and two wolves deciding on what to have for
lunch.  Freedom is a well armed sheep contesting the results of the
decision." - Benjamin Franklin

"The best we can hope for concerning the people at large is that they
be properly armed." --Alexander Hamilton



More information about the bind-users mailing list