Bulk DNS hosting for parked domains

Actually I think I have a good solution now:

• using namesilo's DNS system, you can take any domain's settings and "apply template" and use that in bulk. problem solved!

Don't use CNAME on root (@), it can be applicable per subdomains only like www.
Root must have A record.
Alternative parking method is properly implemented @ParkingCrew but not @matt_bodis

For verification use TXT.

Jurgen Wolf said:

Don't use CNAME on root (@), it can be applicable per subdomains only like www.
@ParkingCrew but not @bodis.

For verification use TXT.

Click to expand...

Yes, Right?! I don't know why bodis says to CNAME the root domain, that doesn't work the way they think it does. I'm using @bodis .. should I just lookup the IP of what they are telling me to CNAME then add that as an A record on root?

There are many articles regarding this matter...
Just 1 link: https://stackoverflow.com/a/757972

I recommend you to use ParkingCrew for such kind of parking...
They provide STABLE IP for root (A record).

That stackoverflow article explains what the issue is (which I'm well aware) but not how to solve it.

Unless you are simply suggesting don't use bodis.

But I'm guessing I can lookup the cname, and add the IP as an A record. It might break later on if bodis changes the IP though. And I'll have to add the domain manually to bodis.

Hi

seems like complicated issue, just to verify at afternic

say that only because.... if you park at bodis, then you might get inquiry from them, that you can negotiate thru escrow and save on that commission afternic charges.

don't know if it was verified or not, but I sold a name thru afternic recently, which was parked at Fab,

so I realize the scope that afternic has and hope you got or get, the issue solved.

imo...

Yes, you can lookup Bodis IP, but this solution is not reliable... because their IP may be changed at any time...

Alternative scheme:
at your provider/registrar set 301 redirect from root to www.
and Bodis CNAME for www.

Hello Brian,

I followed up with your email a short time ago, but if you're attempting to forward your domains at the root level, please point your A records directly to our parking server IP: 199.59.242.150. This should free up your TXT records over at namesilo.com.

Also, this IP address has remained unchanged for some time now, so you shouldn't need to update it any time soon.

Thanks.

Brian Klug said:

Yes, Right?! I don't know why bodis says to CNAME the root domain, that doesn't work the way they think it does. I'm using @bodis .. should I just lookup the IP of what they are telling me to CNAME then add that as an A record on root?

Click to expand...

TroyBodis said:

I followed up with your email a short time ago, but if you're attempting to forward your domains at the root level, please point your A records directly to our parking server IP: 199.59.242.150. This should free up your TXT records over at namesilo.com.

Click to expand...

Troy, yes, thanks, I did appreciate the timely and professional response to my support request. Very good for a weekend day. Thank you.

I will suggest that the instructions be changed on your website? The instructions on www2.bodis.com/account/add-domains still tell the user to make a CNAME record on root domain and www which is against RFC spec and thus impossible to follow.

I do see that bodis actually owns the IP block 199.59.240.0 - 199.59.243.255 so that IP probably won't change, which is good.

Only problem is the instructions can't be followed

@Brian Klug

Great points. As of right now, we will keep 199.59.242.150 pointed to parked landers even if we do decide to change IP. Thus, it should not affect you even if a change occurs. If we ever do require an actual change of this IP, we will inform you and other users.

As far as setting CNAME at root level. It is possible with CNAME flattening (which converts CNAME to IP and DNS provider constantly checks and updates to proper IP if it changes). This is supported by some DNS providers such as CloudFlare. But not supported by most, and as you say, not according to RFC specs.

We will make the update on Add Domains page in the near future. Thanks

matt_bodis said:

As far as setting CNAME at root level. It is possible with CNAME flattening (which converts CNAME to IP and DNS provider constantly checks and updates to proper IP if it changes). This is supported by some DNS providers such as CloudFlare. But not supported by most, and as you say, not according to RFC specs.

Click to expand...

My understanding is, even when you can CNAME a root domain, that makes all other entries invalid as you can't have a CNAME and a record of another type on the same level. Even cloudflare's website says as much at support.cloudflare.com/hc/en-us/articles/200169056-Understand-and-configure-CNAME-Flattening.

So it isn't a viable option in general (assuming you want to have a TXT record like I do or anything else other than raw cname) -- even if the DNS provider supports it.

But yes, good news about 199.59.242.150 being stable!

@Brian Klug

That pages starts off by describing ordinary CNAME records.

But with CNAME flattening (which if not mistaken is a fancy word for saying IP address A-record), everything would be OK. The difference between IP address A-record and CNAME flattening is that with CNAME flattening the dns provider would check for any changes to the IP address of the CNAME host record. If the IP changes, it will change it for you automatically. But it's not actually a CNAME. It's just an IP A-record. It just does the work for you in case a change to the IP occurs. By the sounds of it, by a background task unrelated to the actual DNS.

Article ends off by saying that with CNAME flattening you'd be able to use all other records such as TXT records. As a matter of fact, I know it works because I do it with a bunch of domains on Cloudflare that I use for other purposes.

However, most DNS providers don't support 'CNAME flattening'.

I think they posted more about it here: https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/

The IP makes sense, we will update it soon!

This is also called as ANAME by other DNS providers like https://dnsmadeeasy.com/services/anamerecords/

Its official draft: https://tools.ietf.org/id/draft-ietf-dnsop-aname-03.html

The easiest way is to set up your own DNS servers and have them accept any query and return the bodis ip and your set TXT records. Kinda like an open resolver.

Once domains use your DNS servers they'll serve the right data automatically. I'm using a similar setup (more complicated though)and it's a breeze as you don't have to worry about anything. Unless they change their ip that is but they probably are using an anycast ip which shouldn't change unless sh*t hits the fan.

Better yet, point the A record to your own webserver with on demand SSL and proxy them to the bodis lander.