<div dir="ltr">@Peter - Hey mate, I never said our nameservers would server records, I said the server itself would not go looking as it would assume that as it hosts the website, and has DNS records, that it itself is authoritative. This is basically how all Control Panel like systems function (cPanel, Plesk etc).<div>Our nameservers are not responding incorrectly, or at all in this circumstance, it's just the server not making a DNS query as it assumes it has that information already haha!</div><div><br></div><div>@Ian - Yeah that'll do it mate, give that a switch or hit up support and they can help sort that one out for you.<br></div><div><br></div><div>@Christopher - That's exactly what happens. It's also why our server use a resolver and don't query the same nameservers that they update, else ALL servers in that cluster would fail to get the correct address. To make clearer, (and not using the correct resolvers for privacy), our syd1 servers send their DNS records to <a href="http://ns1.syd1.hostingplatform.net.au">ns1.syd1.hostingplatform.net.au</a>, however when those same servers query DNS, they don't query <a href="http://ns1.syd1.hostingplatform.net.au">ns1.syd1.hostingplatform.net.au</a>, this ensures they all get the correct records that the rest of the world see. The sole exception, as mentioned, is that if the server hosts a specific domain, it won't do a DNS check on it externally.<br></div><div><br></div><div>I hope that helps clear it up for everyone!</div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><table cellspacing="0px">
<tbody>
<tr>
<td><img src="https://static.ventraip.com.au/email/ventraip-corporate-mail-gif.gif" alt="VentraIP Australia logo" width="55" height="55"></td>
<td style="padding-left:8px">
<p><span style="font-family:arial,helvetica,sans-serif;font-size:small;line-height:1.5"><strong>Bradley Silverman<br></strong>Technical Operations \\ VentraIP Australia<br><strong>M: </strong>+61 418 641 103 | <strong>P:</strong> +61 3 9013 8464 | <a href="https://ventraip.com.au/" target="_blank">ventraip.com.au</a></span></p>
</td>
</tr>
</tbody>
</table></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 29, 2018 at 3:05 PM Peter Fern <<a href="mailto:ausnog@0xc0dedbad.com">ausnog@0xc0dedbad.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_8311226512227269289moz-cite-prefix">This is indeed a confusing response.<br>
    </div>
    <div class="m_8311226512227269289moz-cite-prefix"><br>
    </div>
    <div class="m_8311226512227269289moz-cite-prefix">Why does your nameserver have records
      for a domain it does not host?  If a user has delegated their DNS
      away to some other nameservers, you should not be serving any
      records from your nameservers, so the described scenario should
      never happen. Sounds like a problem for VentraIP to fix.<br>
    </div>
    <div class="m_8311226512227269289moz-cite-prefix"><br>
    </div>
    <div class="m_8311226512227269289moz-cite-prefix">On 29/10/18 2:38 pm, Bradley Silverman
      wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Hi Matt,
        <div><br>
        </div>
        <div>To answer your specific question, no they wouldn't.</div>
        <div><br>
        </div>
        <div>BUT there is an exception:<br>
          <br>
          If your site was hosting with us it does add one small layer
          of complexity, which often trips people up.</div>
        <div>Servers are very arrogant, and assume they are the be all
          and end all. So for instance, let's say you are using
          Cloudflare as your Nameservers for <a href="http://example.com.au" target="_blank">example.com.au</a>,
          and your domain is with Synergy Wholesale.</div>
        <div><br>
        </div>
        <div>Synergy Wholesale has the nameservers:<br>
          <a href="http://ns1.cloudflare.com" target="_blank">ns1.cloudflare.com</a>
          (I realize that is wrong)</div>
        <div><a href="http://ns2.cloudflare.com" target="_blank">ns2.cloudflare.com</a>  </div>
        <div><br>
        </div>
        <div>Cloudflare has the same nameservers plus:<br>
          An A record pointing to the VentraIP Server you are on (<a href="http://s111.syd2.hostingplatform.net.au" target="_blank">s111.syd2.hostingplatform.net.au</a>)</div>
        <div>A MX record pointing to Outlook 365 for your email</div>
        <div><br>
        </div>
        <div>VentraIP on S111.syd2 has the records:<br>
          An A record pointing to itself </div>
        <div>A MX Record pointing to itself (the default for web hosting
          generally speaking).</div>
        <div><br>
        </div>
        <div>In this circumstance, <a href="http://S111.syd2.hostingplatform.net.au" target="_blank">S111.syd2.hostingplatform.net.au</a>
          will assume it is the DNS host. The issue comes when your
          website has something like a contact form, or another user
          that uses VentraIP (and is on that server) tries to send an
          email, it will try to deliver locally.</div>
        <div>This is where Remote MX (in cPanel) comes into play, it
          tells <a href="http://S111.syd2.hostingplatform.net.au" target="_blank">S111.syd2.hostingplatform.net.au</a>
          that it <i>isn't</i> the email host, and to send the email
          out into the world to find it's own way.</div>
        <div><br>
        </div>
        <div>The other time this will get messy is if you have a sub
          domain defined on S111.syd2 for <a href="http://test.example.com.au" target="_blank">test.example.com.au</a>
          and also have an A record defined at Cloudflare pointing off
          to <a href="http://otherhostingcompany.com" target="_blank">otherhostingcompany.com</a>, the rest
          of the world will go to <a href="http://otherhostingcompany.com" target="_blank">otherhostingcompany.com</a>
          for the domain <a href="http://test.example.com.au" target="_blank">test.example.com.au</a>, but
          s111.syd2 will look at it's own subdomain for the site, only
          important in cases where your website at <a href="http://example.com.au" target="_blank">example.com.au</a>
          actually looks at <a href="http://test.example.com.au" target="_blank">test.example.com.au</a>.</div>
        <div><br>
        </div>
        <div>I hope that answers it and doesn't make it more confusing
          for you!</div>
        <div><br>
        </div>
        <div>
          <div>
            <div dir="ltr" class="m_8311226512227269289gmail_signature" data-smartmail="gmail_signature">
              <table cellspacing="0px">
                <tbody>
                  <tr>
                    <td><img src="https://static.ventraip.com.au/email/ventraip-corporate-mail-gif.gif" alt="VentraIP Australia logo" width="55" height="55"></td>
                    <td style="padding-left:8px">
                      <p><span style="font-family:arial,helvetica,sans-serif;font-size:small;line-height:1.5"><strong>Bradley
                            Silverman<br>
                          </strong>Technical Operations \\ VentraIP
                          Australia<br>
                          <strong>M: </strong>+61 418 641 103 | <strong>P:</strong> +61
                          3 9013 8464 | <a href="https://ventraip.com.au/" target="_blank">ventraip.com.au</a></span></p>
                    </td>
                  </tr>
                </tbody>
              </table>
            </div>
          </div>
          <br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Mon, Oct 29, 2018 at 11:41 AM Matt Selbst <<a href="mailto:matt.j.selbst@gmail.com" target="_blank">matt.j.selbst@gmail.com</a>>
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div dir="ltr">
            <div>Hey Bradley,</div>
            <div><br>
            </div>
            <div>Thanks for your answer. So assuming I'm not using you
              for DNS hosting (e.g. using a third party like CloudFlare
              or AWS Route53) then would your name servers ever be
              involved in DNS queries for my domain?</div>
            <div><br>
            </div>
            -Matt<br>
            <br>
            <div class="gmail_quote">
              <div dir="ltr">On Mon, Oct 29, 2018 at 10:13 AM Bradley
                Silverman <<a href="mailto:bsilverman@staff.ventraip.com" target="_blank">bsilverman@staff.ventraip.com</a>>
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div dir="ltr">
                  <div dir="ltr">
                    <div dir="ltr">Hi Matt,
                      <div><br>
                      </div>
                      <div>A lot of confusing answers in here, even to
                        me and this is my job to understand them.</div>
                      <div><br>
                      </div>
                      <div>To answer your exact question without filler
                        information:</div>
                      <div>Your registrar (Synergy Wholesale, TPP
                        Wholesale, NetRegistry) need to have the
                        Nameserver records (<a href="http://ns1.server.net" target="_blank">ns1.server.net</a> and
                        <a href="http://ns2.server.net" target="_blank">ns2.server.net</a>) for
                        the domain (<a href="http://Example.com.au" target="_blank">Example.com.au</a>). </div>
                      <div>Then your actual nameservers (<a href="http://ns1.server.net" target="_blank">ns1.server.net</a> and
                        <a href="http://ns2.server.net" target="_blank">ns2.server.net</a>)
                        actually require the exact same nameserver
                        records. Trust me, I have seen things go awry
                        when this isn't the case.</div>
                      <div><br>
                      </div>
                      <div>While you are technically reliant on the
                        root, auDA, and Affilias, all their job is to
                        get someones request to the .com.au namespace TO
                        the actual .com.au domains, and not something
                        you ever have to worry about.</div>
                      <div><br>
                      </div>
                      <div>All you need to do is make sure both your
                        registrar and your nameservers point to your
                        nameservers. Does that make sense?<br clear="all">
                        <div>
                          <div dir="ltr" class="m_8311226512227269289m_-4813597323074909736m_843416042495245178gmail_signature">
                            <table cellspacing="0px">
                              <tbody>
                                <tr>
                                  <td><img src="https://static.ventraip.com.au/email/ventraip-corporate-mail-gif.gif" alt="VentraIP Australia logo" width="55" height="55"></td>
                                  <td style="padding-left:8px">
                                    <p><span style="font-family:arial,helvetica,sans-serif;font-size:small;line-height:1.5"><strong>Bradley
                                          Silverman<br>
                                        </strong>Technical Operations \\
                                        VentraIP Australia<br>
                                        <strong>M: </strong>+61 418 641
                                        103 | <strong>P:</strong> +61 3
                                        9013 8464 | <a href="https://ventraip.com.au/" target="_blank">ventraip.com.au</a></span></p>
                                  </td>
                                </tr>
                              </tbody>
                            </table>
                          </div>
                        </div>
                        <br>
                      </div>
                    </div>
                  </div>
                </div>
                <br>
                <div class="gmail_quote">
                  <div dir="ltr">On Mon, Oct 29, 2018 at 6:16 AM Matt
                    Selbst <<a href="mailto:matt.j.selbst@gmail.com" target="_blank">matt.j.selbst@gmail.com</a>>
                    wrote:<br>
                  </div>
                  <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <div dir="ltr">Right, so for the sake of clarity as
                      I understand it from the responses - I'm reliant
                      on root, auDA and Afilias name servers but NOT my
                      registrar e.g. Synergy Wholesale, TPP Wholesale,
                      NetRegistry etc....<br>
                      <br>
                      <div class="gmail_quote">
                        <div dir="ltr">On Mon, Oct 29, 2018 at 5:59 AM
                          Peter Fern <<a href="mailto:ausnog@0xc0dedbad.com" target="_blank">ausnog@0xc0dedbad.com</a>>
                          wrote:<br>
                        </div>
                        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 28/10/18 11:58 pm,
                          Chad Kelly wrote:<br>
                          > On 10/28/2018 11:10 PM, <a href="mailto:ausnog-request@lists.ausnog.net" target="_blank">ausnog-request@lists.ausnog.net</a>
                          wrote:<br>
                          ><br>
                          >> The original post was asking if the
                          registrar is relied upon here <br>
                          >> (and the answer is no).<br>
                          > But the nameservers themselves still need
                          to be listed at the <br>
                          > registrar level so that they can be found
                          on the public internet. <br>
                          > Otherwise you run into issues with dns
                          lookups and them not being able <br>
                          > to resolve your dns correctly.<br>
                          > They call this having registry hosts.<br>
                          ><br>
                          <br>
                          registrar != registry<br>
_______________________________________________<br>
                          AusNOG mailing list<br>
                          <a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
                          <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
                        </blockquote>
                      </div>
                    </div>
                    _______________________________________________<br>
                    AusNOG mailing list<br>
                    <a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
                    <a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
                  </blockquote>
                </div>
              </blockquote>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <p><br>
    </p>
  </div>

_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" rel="noreferrer" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote></div>