Wildcard records???

[Tani Hosokawa]

Well... I saw recently a system on freshmeat.net that was designed to keep
hosts file synchronized between servers, designed for university type
setups with hundreds of machines.  I forget the name, but someone else
might remember?

On Sat, 3 Jul 1999 jeremy at xxedgexx.com wrote:

> 
> /etc/hosts on each machine is must harder to maintain then a single name
> server.
> 
> I think my best course to try and convince them to rm the wildcard MX.
> 
> -jeremy
> 
> > You could start using your /etc/hosts file...
> > 
> > On Fri, 2 Jul 1999 jeremy at xxedgexx.com wrote:
> > 
> > > This does kinda work, but unfortunately it breaks many other things on the
> > > system.  Application that address thing by hosts only and not FQDN's
> > > break.
> > > 
> > > -jeremy
> > > 
> > > > An easier, but possibly unpleasant alternative... remove the search and/or
> > > > domain lines from your resolv.conf.  I expect that's why it'd doing that.
> > > > First it checks ahahahah.com, then it goes through all your search terms..
> > > > with no search terms, it'll just stop trying to resolve immediately.
> > > > 
> > > > On Fri, 2 Jul 1999 jeremy at xxedgexx.com wrote:
> > > > 
> > > > > 
> > > > > Hmm, well I don't really want the default behavior to allow such a thing.
> > > > > I think their goal was to allow people to mail anything.company.com for
> > > > > whatever reason.  But it's screwing up mail because if someone emails
> > > > > captainkirk at idonexist.com, it still gets pushed to the smtp server.
> > > > > 
> > > > > -jeremy
> > > > > 
> > > > > > I haven't checked into this, but you might be able to put a *.com.company.com in
> > > > > > your sendmail.cw, so anything coming into that would be acceptable.  I don't
> > > > > > know for sure if this is possible, but might be worth looking into.
> > > > > > 
> > > > > > Dan
> > > > > > 
> > > > > > jeremy at xxedgexx.com wrote:
> > > > > > > 
> > > > > > > Hello!
> > > > > > > 
> > > > > > > Is there any safe way to create a wild card record.  I just start working
> > > > > > > for a new company and they have a * in their record which appears to be
> > > > > > > causing a lot of problems with mail.  I've always stayed away from it
> > > > > > > cause I thought it was considered bad practice.
> > > > > > > 
> > > > > > > Problems we're having is with mail.  If we send mail to an invalid domain,
> > > > > > > it uses that name as a hostname.  For exmaple, I send mail to
> > > > > > > blah at ahahahahaha.com, it bounces but in the header we see this:
> > > > > > > 
> > > > > > > blah at ahahahahahaha.com.company.com
> > > > > > > 
> > > > > > > which is incorrect.  It causes load and unwanted behavior because no
> > > > > > > matter what address we put in place, it hits our smtp server because it
> > > > > > > put company.com at the end of any address.
> > > > > > > 
> > > > > > > Is there a safe way to use wildcard records, or do you think I should
> > > > > > > begin to convince them on getting rid of it.
> > > > > > > 
> > > > > > > Thanks
> > > > > > > -jeremy
> > > > > > > 
> > > > > > > http://www.xxedgexx.com | jeremy at xxedgexx.com
> > > > > > > ---------------------------------------------
> > > > > > > Y2K.  We're all gonna die.
> > > > > > 
> > > > > 
> > > > > 
> > > > > http://www.xxedgexx.com | jeremy at xxedgexx.com
> > > > > ---------------------------------------------
> > > > > Y2K.  We're all gonna die.
> > > > > 
> > > > > 
> > > > 
> > > > ---
> > > > tani hosokawa
> > > > river styx internet
> > > > 
> > > > 
> > > 
> > > 
> > > http://www.xxedgexx.com | jeremy at xxedgexx.com
> > > ---------------------------------------------
> > > Y2K.  We're all gonna die.
> > > 
> > 
> > ---
> > tani hosokawa
> > river styx internet
> > 
> > 
> > 
> 
> 
> http://www.xxedgexx.com | jeremy at xxedgexx.com
> ---------------------------------------------
> Y2K.  We're all gonna die.
> 
> 

---
tani hosokawa
river styx internet