14 {{ upvoteCount | shortNum }}
14 {{ upvoteCount | shortNum }}

Handling DNS in Multi IP Blog Network

by GuerrillaIM
12 replies
  • SEO
    • |
Right... Here's what's puzzling me today:

What is the point of paying through the nose for gazumpteen website IP's if they all use the same DNS server IP?

Cant anyone say "FOOOT PRIIIIINT"?

I tried asking a network guy what I should do. His mouth moved.... Words did come out... Thats about all I can tell you from that exchange. If IPTables are your bag and routing issues come as second nature then you two would have had a HOOT!

Back in my world where I don't understand what the hell anyone is going on abouit, I am confused as hell.

I have read several tutorials on hostgator website but nothing that actually addresses my problem.

Gone round in circles with 4 different tech supports from hosting company (SEOHosting.com a.k.a HostGator). One of them even made an effort to understand what I wanted... he even gave me the great advice of "don't worry about it". Smashing chap... 5/5 rating heading his way!

It might be that I have to just lump it or setup a VPS with multiple IP's to handle my DNS, but I was under impression it could all be done with WHM & Cpanel from SEOHosting.com.

I realize this is probably over most peoples heads (the thread title alone probably sent many running for the hills), but I know several warriors have a similar setup as me. Anyone want to break cover and make an improvement on "don't worry about it"?
#blog #dns #handling #multi #network
  • Profile picture of the author seogoat
    I'm not sure if I quite know what you mean but I'll make a suggestion. Sorry if I am stating the obvious. But do you think it would be more appropriate to host with several different hosting companies rather than just the single one. That way you can host groups of ten or so domains on different dns servers or something along those lines.

    I do not think that Google actually looks at DNS, but if I were hosting loads of different domains I would at least want to be 100% safe because Google can, as you know, change the way they view sites with a click of their fingers.
    {{ DiscussionBoard.errors[2923989].message }}
    • Profile picture of the author GuerrillaIM
      Originally Posted by seogoat View Post

      I'm not sure if I quite know what you mean but I'll make a suggestion. Sorry if I am stating the obvious. But do you think it would be more appropriate to host with several different hosting companies rather than just the single one. That way you can host groups of ten or so domains on different dns servers or something along those lines.

      I do not think that Google actually looks at DNS, but if I were hosting loads of different domains I would at least want to be 100% safe because Google can, as you know, change the way they view sites with a click of their fingers.
      It definately an alternative, but the practical aspect of it puts me off. I use a software that integrates with the control panel to automate all my blog installation/configuration/updating/content posting. I think if I spread around too many different companies I will be causing problems for myself.

      Also the price seohosting.com is good for the number of IP's you get.
      {{ DiscussionBoard.errors[2924025].message }}
      • Profile picture of the author jasonthewebmaster
        Banned
        Originally Posted by GuerrillaIM View Post

        It definately an alternative, but the practical aspect of it puts me off. I use a software that integrates with the control panel to automate all my blog installation/configuration/updating/content posting. I think if I spread around too many different companies I will be causing problems for myself.

        Also the price seohosting.com is good for the number of IP's you get.

        To build on this...


        I use WHM and WHMCS and you can connect WHMCS to many different servers at many different hosts. This would give you a way to manage them all. Hope this helps!
        Jason
        {{ DiscussionBoard.errors[3810790].message }}
  • Profile picture of the author KirkMcD
    Use a public dns server that can look to your server for the dns info (Secondary DNS), like everydns.net.
    {{ DiscussionBoard.errors[2924249].message }}
    • Profile picture of the author GuerrillaIM
      Originally Posted by KirkMcD View Post

      Use a public dns server that can look to your server for the dns info (Secondary DNS), like everydns.net.
      Thanks Kirk. I just checked out their site and looks like they are merging with DynDns.org. I use DynDNS for my secondary DNS on my server incase my local DNS server crashes.

      Will I be able to get away with their free service or am I looking at $15/yr per domain for the pro package?
      {{ DiscussionBoard.errors[2924308].message }}
  • Profile picture of the author GuerrillaIM
    UPDATE: Got through to a helpful guy at support (5th times a charm). He said I could have the DNS IP & domain the same IP as the CPanel it's hosted on.

    I updated my DNS to give it a go but will take a few days to sort out. If it works then it's a result.

    PHP Code:
    C:\begin.exe /holding -breath 
    {{ DiscussionBoard.errors[2924692].message }}
  • Profile picture of the author GuerrillaIM
    Thought it was too good to be true. I can setup ns.mydomain.com but it still uses the IP adress that is assigned to all SEOHosting.com users (Yes, I asked them and this is the case, this DNS IP is exclusively for their SEOHosting.com clients).

    Back to the drawing board.
    {{ DiscussionBoard.errors[2925121].message }}
  • Profile picture of the author GuerrillaIM
    Their support techs just say that I am wrong but even if Google dont use this to track down interlinked networks, how long before they start doing it?

    The really bad thing about this is it gives 2 identifiers.

    1. Identifies all your sites as your primary DNS IP will be unique to just the sites you own, even though the website IP will be different.
    2. Puts out a big marker to show google you have a SEO hosting account.

    Take this example below. 3 cpanels on seprate IP's. Each one has its own domain as nameserver but they take your first Cpanel Ip as the same as your primary DNS IP and use common seohosting.com IP for secondary DNS.



    OK, is it just me or does this seem retartded?
    {{ DiscussionBoard.errors[2925179].message }}
  • Profile picture of the author dburk
    Hi GuerrillaIM,

    Many domain name registrars include DNS service for your domain name. So if you are using a registrar like Godaddy you can just point your domain to the IP address of your website. Since their names servers are common and used by millions of websites, there is no way practical to connect your websites through their name servers. I have done this for numerous websites for many years.

    One thing you will never be able to hide is who owns the IP blocks that your website is hosted on. So no matter what DNS service you use, you are always resolving an IP address that can be identified as being owned by your host.
    Signature

    * Get Results - Outsource Your PPC Management |
    *     Don Burk Advertising & Marketing - www.donburk.com

    {{ DiscussionBoard.errors[2925224].message }}
    • Profile picture of the author GuerrillaIM
      Originally Posted by dburk View Post

      Hi GuerrillaIM,

      Many domain name registrars include DNS service for your domain name. So if you are using a registrar like Godaddy you can just point your domain to the IP address of your website. Since their names servers are common and used by millions of websites, there is no way practical to connect your websites through their name servers. I have done this for numerous websites for many years.

      One thing you will never be able to hide is who owns the IP blocks that your website is hosted on. So no matter what DNS service you use, you are always resolving an IP address that can be identified as being owned by your host.
      This sounds like the solution I need. I made mistake of registering all my .co.uks with 1&1 and I dont think they have this but I have my .coms with namecheap so I guess they will have it.

      Using a common nameserver like that would be ideal. Also the IP owner is general aswell as its same info as all other sites with company. I just didn't like the fact they setup the DNS servers in a way to make your whole network easily identifyable as using the seo package.

      Just got to tweak SOA & SPF record now and I think I have covered my tracks well enough... fingers crossed.

      Heading to bed, will test it out tommoz.

      ***EDIT***

      If I had access to RIPE database I could have some fun identifying peoples network. Simple little app could just run in background searching for the seohosting.com default dns then grouping them by primary DNS IP. Would be fun to see what people are using all their networks for.
      {{ DiscussionBoard.errors[2925579].message }}
      • Profile picture of the author seogoat
        Good luck with it. I'm sure you'll get it sorted. It looks a bit of a nightmare. Hope you don't have to swap servers again after setting it all up.
        {{ DiscussionBoard.errors[2925682].message }}
  • Profile picture of the author GuerrillaIM
    As always the solution was blindingly simple. Dburk had it right! I just needed to forward the A record.

    Its amazing that none of the so called server experts I talked to suggested this. I had all sorts of offers to create VPS for me or to do elaborate server settings. I guess good/honest server guys are like rocking horse sh**
    {{ DiscussionBoard.errors[2928547].message }}

Trending Topics