Erm, what does that have to do with DNS lookups? 
Erm, what does that have to do with DNS lookups?
Nothing at all, except that it stops this behaviour:
... when you have no DNS
servers configured and mistype "configt", or some other command that
doesnt exist and it tries to resolve it through broadcast several times.
More specifically, IOS command mode will assume by default that any non recognised command is actually a hostname which it should try to connect to - a fossilised relic of times past, when routers were often terminal servers. You can stop it doing this by using "transport preferred none" on the appropriate line configuration.
Nick
Yup, I knew that, sorry.
Ryan Rawdon wrote:
Anybody actually on that list? Most of the serious mailops work is on
some other, entirely different lists.
And why do people have to think nanog is solely for packet pushing
related ops? Email is operational, and its often the first ops
failure that your users notice, right after the ones that go "I cant
get to my pr0n".
Suresh Ramasubramanian wrote:
Anybody actually on that list? Most of the serious mailops work is on
some other, entirely different lists.
I followed up to John's message there. We're currently seeing
intermittent timeouts when connecting TCP/25 on ib1.charter.net as well
as timeouts after the TCP session is established.
Thanks,
Meta: I'm one of the mailop list admins...
Anybody actually on that list? Most of the serious mailops work is on
some other, entirely different lists.
There are almost 400 on the list now, and it grows with every single
mention here and on other lists.
The reason Andy created it was in response to the plethora of "any ISP
XYZ mail admins contact me off list" messages NANOG used to see, along
with several threads which some posters saw as non-operational.
I'd be very pleased to know about the other lists, especially as in
previous years I've always come up against brick walls - "you're not big
enough, go away" or "we don't know you, go away". Not especially
helpful, especially as the latter case would be resolved by allowing
more open subscription.
And why do people have to think nanog is solely for packet pushing
related ops? Email is operational, and its often the first ops
failure that your users notice, right after the ones that go "I cant
get to my pr0n".
Email is operational, yes. But there are many on NANOG who feel that it
isn't, judging by the reaction in the past to long-running threads about
it.
Graeme
Yes, that is a problem with vetted communities at some stage or the
other of their vetting career. Try asking again, depending on where
you asked you might get a different answer now.