making a internall website with dns

[metro2012]

i have a website setup internally using apache. its website.met. my ip is 192.168.1.99 in the domain controller i made a new A record point website.met to 192.168.1.99 i flushed the dns on the client and the client cannot resolve the website. y does it not work?

[CPressland]

Well, the Web Server should be using it's full FQDN. So, if your domain was example.com then the Web Server should be something like webserver.example.com and you'd only need to setup a new a record for WebServer.

[still1]

i have a website setup internally using apache. its website.met. my ip is 192.168.1.99 in the domain controller i made a new A record point website.met to 192.168.1.99 i flushed the dns on the client and the client cannot resolve the website. y does it not work?

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

[CPressland]

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

I'm fairly sure Windows Server's DNS doesn't require Authentication or IP-Whitelisting.

[metro2012]

Well, the Web Server should be using it's full FQDN. So, if your domain was example.com then the Web Server should be something like webserver.example.com and you'd only need to setup a new a record for WebServer.

the domain is called mydomain.local so would i have to make a A record pointing at mydomain.local.website.met and then create a CNAME with that pointing to website.met ?

one thing i can think of is the user's permission to the domain controller to resolve the dns!!

no, thats not the case.

[CPressland]

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

[metro2012]

No, you'd make an A record called website.met.mydomain.local.

Your Domain Name goes after the Hostname of the Device. If you want to be able to hit 'Website.met' directly with no further intervention then you need to create a new forward lookup zone called .met and add website* to it.

i made a A record and it automatically put mydomain.local to its right but I removed it and left it website.met but I think it made its own foward lookup zone..........

obviously i made a mistake but sadly im not the network admin so i cant be saying lets try this and that....

[CPressland]

Well, your Network admin WILL know what he needs to do to setup something like this. Just make sure the hostname on your Linux box thats running the WebServer is setup correctly and has a Static IP.

[metro2012]

Well, your Network admin WILL know what he needs to do to setup something like this.

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

told him 2day and here it is....

Just make sure the hostname on your Linux box thats running the WebServer is setup correctly and has a Static IP.

it is a windows box and yes: it is static.

[CPressland]

he doesnt. i just told him that i wanted to point website.met to my ip because i am running a web site with apache there and he told me that i would have to tell him how to do it as he does not know how to.

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

it is a windows box and yes: it is static.

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

[metro2012]

Then he shouldn't be a working in Networking - my partners 9 year old can already handle DNS configuration.

go tell him (my boss) that........he didnt even know where to go in windows server to do it.

If it's Windows, Bind to the Domain and it's instantly resolvable. Active Directory will automatically add the appropriate A Records.

so therefore, I create a new A record and just leave the mydomian.local that is automatically appended to the right. ill try asking him to do tha if it doesnt work, then i guess ill just leave it alone.

[CPressland]

You don't need to create anything, if the Windows Server that is running the Apache Server is joined to the domain as website.met then it'll automatically be resolvable.

[metro2012]

You don't need to create anything, if the Windows Server that is running the Apache Server is joined to the domain as website.met then it'll automatically be resolvable.

?

i have apache server on pc 1 (my pc) dc is another pc, pc 2, i want the apache server to accessed by pc 3, 4, 5 (other pcs) on dc. all connected to dc.

it is not on ws/dc............

[CPressland]

Okay

Domain name is mydomain.local

Domain Controller for example is called dc.mydomain.local

Apache Server is called website.met.mydomain.local

Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

[metro2012]

Okay

Domain name is mydomain.local

Domain Controller for example is called dc.mydomain.local

Apache Server is called website.met.mydomain.local

Other PCs are called PC1.mydomain.local, PC2.mydomain.local, PC3.mydomian.local etc

When website.met is joined to mydomain.local it gets the FQDN of website.met.mydomain.local

When a user types http://website.met into a Web Browser it'll search the network for a name containing website.met and then try the outside world. This is called a Search Domain, when it finds website.met.mydomain.local it'll automatically connect to the correct IP address and load the page.

yes. exactly. the first five lines describe exactly the situation.

so how would i set that up on the dns server????

[CPressland]

What is the name of the Apache server?

Start > Right Click Computer > Properties

[Wiggz]

yes. exactly. the first five lines describe exactly the situation.

so how would i set that up on the dns server????

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

[metro2012]

What is the name of the Apache server?

Start > Right Click Computer > Properties

PC1

all pcs here (except the dc) are named lik that with the number being the differece.

I think the answer of "You don't" is particular pertinent here.

As CPressland has stated, the fact that the Apache Web server (presumably running on a Windows box connected to the "domain" in question), the Domain's DC, and the clients actively looking to connect to the Apache Website will all be on the same domain, and connected accordingly, means you don't have to create a DNS record. As long as your Apache web server is called "website.met" you're all good!

Just make sure you are connected to the domain and as CPressland has stated, the DNS records will automatically be created on the DNS server

are you saying "it just works"? im sure id have to make a entry for this apache virutal hsot to be seeable by all....

[+BudMan MVC]

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

[metro2012]

"DNS records will automatically be created on the DNS server"

That is if the domain is not jacked up -- with a network admin that does not know how to create a A record, or where even to look for dns on the DC?

I am taking odds that prob not ;)

so you called your machine website.met ?? Really that is an odd name for a computer, could you post the output of hostname. And then just do a nslookup for the name that is output from hostname.

example

C:\Windows\System32>hostname

i5-w7

C:\Windows\System32>nslookup i5-w7

Server: pfsense.local.lan

Address: 192.168.1.253

Name: i5-w7.local.lan

Address: 192.168.1.100

C:\Windows\System32>

edit: Well if your computer is called PC1, then no its not just going to work.. You need to create the records in dns to point to the name you want for your website.

Do you have access to dns on the DC?

here

http://support.microsoft.com/kb/324260

How To Configure DNS Records for Your Web Site in Windows Server 2003

Same thing if 2k8 or 2k8r2, etc.. Send that link to your so called network admin

no my machine is called PC1. the apache server has a virtual host called website.met the apache server is on PC1

[+BudMan MVC]

here -- this is how you do it if you want to resolve website.met to your 192.168.1.99 address

See its a forward zone called met, with A record of website

I had to change what server I did my nslookup too, because I do not use that box as my dns

you could also do it with a cname pointing to your pc1.whaterdomainyourusing -- but lets just keep it REAL SIMPLE!!

[metro2012]

the dc is windows small business server 2003 r2

[+BudMan MVC]

Doesn't matter! Interface is the same, create a new primary forward zone called met, then A record of website.

Right click forward lookup zones, new zone, primary -- call it met

Then right click then new zone met and create A record website with your IP you want to point it too

[CPressland]

Okay - if all else fails i'm happy to offer a TeamViewer session to the server to do this. What, 11 seconds of work?!

[Wiggz]

perhaps :)

Everyone has different strengths and weaknesses though. Unfortunately I'm a jack of all trades and master of none.....so I end up giving very limited advice about a RANGE of stuff :)