# OT: What is the best DNS for wildcard subdomains?

**URL:** <https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322>\
**Category:** Rails\
**Created:** [March 8, 2009, 6:04pm UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322 "2009-03-08T18:04:37Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 8, 2009, 6:04pm UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/1 "2009-03-08T18:04:37Z")

</div>

I am having issues with netfirms in that in the past and right now  
certain subdomains result in a failure to direct the request to my  
servers.

I need to find somewhere that is reliable and that can handle wildcard  
subdomains.

Any suggestions?

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 8, 2009, 10:07pm UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/2 "2009-03-08T22:07:20Z")

</div>

Hey Chris -

On 8-Mar-09, at 1:04 PM, Chris O. wrote:

> I am having issues with netfirms in that in the past and right now  
> certain subdomains result in a failure to direct the request to my  
> servers.
> 
> I need to find somewhere that is reliable and that can handle wildcard  
> subdomains.
> 
> Any suggestions?

I’ve never run my own dns, or compiled bind - but I can say that  
[easydns.com](http://easydns.com) is a joy to use; wildcards et all.

Jodi

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 9, 2009, 2:38am UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/3 "2009-03-09T02:38:12Z")

</div>

You should probably diagnose the actual problem so that you don’t waste  
a lot of time migrating a broken configuration only to have it remain  
broken.

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 9, 2009, 3:33am UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/4 "2009-03-09T03:33:52Z")

</div>

Jodi S. wrote:

> I’ve never run my own dns, or compiled bind - but I can say that  
> [easydns.com](http://easydns.com) is a joy to use; wildcards et all.
> 
> Jodi

Thanks for the advice Jodi. I signed up and was able to get everything  
working. Hopefully I never see this problem again.

BTW, when I signed up I added your name to the referral slot, so  
hopefully you get something out of this.

Thanks again.

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 9, 2009, 3:49pm UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/5 "2009-03-09T15:49:48Z")

</div>

On 8-Mar-09, at 10:33 PM, Chris O. wrote:

> Thanks for the advice Jodi. I signed up and was able to get  
> everything  
> working. Hopefully I never see this problem again.
> 
> BTW, when I signed up I added your name to the referral slot, so  
> hopefully you get something out of this.
> 
> Thanks again.

8-))

---

<div class="post-metadata">

**Author:** ![chrisolsen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/c6cbf5/32.png) [@chrisolsen](https://www.ruby-forum.com/u/chrisolsen)\
**Post date:** [March 9, 2009, 3:37am UTC](https://www.ruby-forum.com/t/ot-what-is-the-best-dns-for-wildcard-subdomains/162322/6 "2009-03-09T03:37:04Z")

</div>

Ranjeet Smith wrote:

> You should probably diagnose the actual problem so that you don’t waste  
> a lot of time migrating a broken configuration only to have it remain  
> broken.

The first time netfirms admitted to the problem being on their side so  
the root of the problem has been removed 🙂
