Foo - DNS wildcarding
Bikeforums.net is a forum about nothing but bikes. Our community can help you find information about hard-to-find and localized information like bicycle tours, specialties like where in your area to have your recumbent bike serviced, or what are the best bicycle tires and seats for the activities you use your bike for.
09-14-10, 05:38 PM
I don't know DNS, and need to make a request. However, I want to make sure I don't hose our services when someone does what I ask.
Suppose we have an entry such that
*.bar.com resolves to some IP
I want another entry
*.foo.bar.com to resolve to a completely different IP
Can I do this, or will the entry for *.bar.com trump the entry for *.foo.bar.com rendering the entry I want useless?
09-14-10, 09:11 PM
*.foo.bar.com will resolve before *.bar.com
*edit: on most DNS servers this is the case. Some older versions of BIND require *.foo.bar.com to come before *.bar.com in the zones file.
this should be in the bamboozle thread.
09-15-10, 03:36 PM
In the end, I decided to request that *.bar.com point to an IP on the EC2 cloud since I could operate foo.bar.com and any subdomain of that from one place very easily.
The reasons are driven by business logic and there's no nefarious angle. But we'll see how paranoid the local admins are since that would effectively transfer the entire namespace to an area where uni computing has no control and services can be created thin air or vaporized in seconds. If our own office were a little less conservative, we could just buy a domain and manage it ourselves.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.