|
I didn't realise dealing with IT gurus could be so tiresome... There was a bit of to and fro beforehand but basically we figgered out we couldn't set the nameservers of a site to change, so we had to do the A record. This guy handles the registry stuff, I do the hosting, so I just need him to add an A record for the whole domain, I'm not particularly savvy when it comes to the networking side of things, but honestly how long does it take for someone who does this as a job to get it? Ok back from Phillip Island...
I'm not much of a network geek so unsure what exactly you need, here's the IP for the "A" record: ###.###.###.###
Yes this is what was required and has been entered into the MelbourneIT DNS manger.
Providing it is the correct IP address the site will be backup with-in 2 - 72 hrs.
... Couple boring emails about nameserver stuff ... The IP address you supplies is also correct as it now forwards www requests to the servage web server, therefore the name server is correctly working as per the supplied IP address, but the web server is not routing it to the right location.
Ok the site is now up if you prefix it with WWW, but without the WWW (and any other subdomain) it just 404's. Ok it looks like only the WWW part has had the a record set, it also needs to have the domain itself (no www) set to the IP ###.###.###.###
Not sure what you mean all I can tell you is that the MelbourneIT records have been set as we have done so for over 60 other clients (as per the standard convention used by every domain host provider all over the world) and we have never experienced this type of issue.
I don't think servage have it quite right yet Please have it revisited.
I have checked and found that you are not using the servage nameservers for the domain aqueous-water.com.au, you have set our IP address for only www.aqueous-water.com.au
You will need to set the A record for aqueous-water.com.au as well to the IP ###.###.###.###
You can only set a A record to point to a IP address, url's can only be set as a CNAME. I will added it but why was this information not provided initially.
Like I said I'm no network geek, I just forwarded the IP address.
At a guess it might have worked for both www and non if A record was set to *.A-W.com.au to start with instead of doing them individually, dunno.
What has been requested is invalid and is not allowed by the MelbourneIT domain servers. As I stated you normally have one or the other hence why I never added both and as it turns out its not allowed.
So you're not allow to set an A record for just aqueous-water.com.au? Seems odd given that all the other records are like that, according to http://who.is/dns/aqueous-water.com.au it's only the A record which has been set with the WWW prefix, which is why I suspect www.A-W.com.au resolves but A-W.com.au doesn't.
No please do not miss quote me I said that a "a record can only be a IP address. Again this is a global standard.
Yes, but I'm left unsure what it is that's holding things back.
Can you set the A record for aqueous-water.com.au sans WWW to the IP I supplied?
The www.aqueous-water.com.au is already done, the hold up is the non-WWW portion.
What do you mean by non-www portion?
http://aqueous-water.com.au
This was done two days ago as per my email.
Yah, and as I noted it appears to have been done for WWW.aqueous-water.com.au - which works fine - but not just aqueous-water.com.au, sans WWW.
I have tried it from numerous computers within our network and externally and it does not appear to work at all. Yes it does goto a text file version of the site but that is as far as it gets.
This is because the non-WWW portion is not resolving.
Once that resolves correctly the site will look correct, as it is attempting to reference CSS etc files on the non-WWW version which obviously just 404 out.
I can't (easily) get into the admin back-end until the non-WWW bit is sussed out, which as far as I can tell requires the A record to be added.
Interesting never had to do this with any other site. Usually only need to set either a record or CNAME that is it. Anyway I will wait for a update from you
The difference is that the A record has been set for WWW.aqueous-water.com.au - hence that is the only domain that is resolving. You could do the same with any subdomain, eg http://porn.aqueous-water.com.au/ gives the same result as just aqueous-water.com.au ...
I think you need to set the A record for JUST the aqueous-water.com.au domain, which may require an asterisk prefix - I'm not sure.
See the link I sent earlier, ALL the other records are just for the main domain, but for some reason the A record has been set for the WWW subdomain only.
http://who.is/dns/aqueous-water.com.au
A entry has been added to allow lookup with or without the need for the www prefix. This has not resolved the problem as it is a internal DNS issue within the web server. This is further proven by the fact that if you ping the domain name the web server IP address is responding therefore it is reaching the correct address.
Regardless if you attempt to access the site with or without the www prefix the result is the same, the site is not displaying correctly.
Nope, site looks fine now, it worked, ta.
Can we please get pass this it is not the wrong DNS domain. Let me spell it out for you it is a internal issue on the web server the screenshot proves this. If you would like further proof you can call MelbourneIT youeself.
That's exactly what it should be showing - a new install of a CMS, it wasn't yesterday because of the non-WWW thing, but you fixed that, now I can work on the site.
Irrespective of if the web site could be accessed via a non-www address makes no difference to the publishing of the web site, but how ever you would like to justify it makes no difference to me.
I know that I was presenting the facts which where correct and consistent in my findings. Considering your last email claimed that the site was up but now the story has changed, you may want to chose your words more carefully before making more claims.
What are you on about?
I don't care, the stuff I said yesterday was correct and I'm not doing any historical revisionism, read it again if you like. It was accessible via WWW but not via non-WWW until you made the changes I suggested, you presented the facts as far as you knew, you just didn't know all of them, no prob bob. All sorted now so no need to get huffy.
Again not being able to access it via a non-www address has no bearing on why the site was not publishing correctly.
Yes it does, here's what I said yesterday:
This is because the non-WWW portion is not resolving.
Once that resolves correctly the site will look correct, as it is attempting to reference CSS etc files on the non-WWW version which obviously just 404 out.
I can't (easily) get into the admin back-end until the non-WWW bit is sussed out, which as far as I can tell requires the A record to be added.
Now the non-WWW bit is resolving and so the site looks correct, all goodski.
If you say so but this is the only web host system I have ever worked on and I have worked on many that allegedly requires a non www entry before it will work
The logic is simple, WWW is just a subdomain, as I said it could be porn.A-W.com.au or whatever, if you ONLY put in a record for a subdomain that is the only thing that will work, if you put in a record for the entire domain - ie without the WWW bit - then the whole domain will work, which is what we've got now.
Go through your other websites if you like, you'll find them to be the same - ie not registered as just WWW like A-W was originally.
Ok thanks
I'm just glad I'm not in IT.  
|
Related Topics
Tue, 11 Nov, 2008 - 17:35
Your Privacy Choices