Recommended Posts

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!!

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.

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.

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....

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.

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.

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.

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............

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.

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????

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

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....

"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

"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

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

post-14624-0-23822200-1337161780.jpg

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!!

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

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Google is opening the world's first AI museum in Los Angeles by Ivan Jenic Image via: Google Ever since AI image generators went mainstream, the debate over whether AI-generated art is real art hasn't let up. Those who don’t consider AI to be art say that if a machine does the creating and anyone can prompt it, there’s no skill involved, and therefore no art is produced. The counter-argument is equally persistent, as defenders of AI-generated artworks often claim that AI is just a tool, and that every major technological breakthrough, like the camera or the computer, was met with the same skepticism before eventually being accepted as a legitimate creative medium. Google’s position in this debate is clear. Which is no surprise, as the company is investing billions in AI infrastructure. And now, in efforts to encourage people to use its AI even more, Google is opening Dataland on June 20, which it's calling the world's first AI arts museum. Located inside The Grand LA, a Frank Gehry-designed building in Los Angeles, the museum spans 25,000 square feet. The museum is built around a collaboration with media artist Refik Anadol, who has worked with Google since 2016. The inaugural exhibition is called Machine Dreams: Rainforest, and is powered by an AI model trained on “an extensive dataset of the natural world.” It generates 1.2 billion pixels of visuals in real time and reacts to visitors dynamically. The space also generates soundscapes, real-time emotion sensing, and algorithmically produced scents. Image via: Refik Anadol Studio / Google Google says that the museum is powered by its Gemini models, which run on Google Cloud. So, everything is generated inside one of Google’s AI data centers and is streamed to the museum. Alongside the museum opening, Google Arts & Culture is funding an AI Artist Residency, giving four artists $25,000 grants each, along with mentorship from Refik Anadol Studio and access to Google's machine learning tools. Their work will be shown at Dataland and on the Google Arts & Culture website later this year. Google’s AI museum will undoubtedly initiate a fired-up debate on social media, and we can’t wait to see the first reactions. Via: Smithsonian Magazine
    • Calling GTA 6 overhyped crap doesn’t make you edgy, it just makes you sound like someone who hasn’t enjoyed anything since the PS2 era.
    • I’m not arguing whether Rockstar likes money. Obviously, they do, they’re a business. I’m saying this isn’t new. They’ve always launched console first. This is just how Rockstar operates.
    • I'm not sure how old the school is, but they've been doing this since GTA 3. Back in those days we'd be lucky for game companies to release on the PC at all. And with the current state of Sony (or Microsoft) their gaming wing won't be getting a penny from me.
    • We now know when and how the Universe may truly end by Sayan Sen Image by Marek Pavlík via Pexels| Not representative A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. The research, published in the Journal of Cosmology and Astroparticle Physics, was conducted by Tye, Horace White Professor of Physics Emeritus at Cornell University. Using recent observations from major dark-energy surveys, Tye and his collaborators developed a cosmological model that predicts the universe could have a total lifespan of about 33 billion years. Since the universe is currently estimated to be 13.8 billion years old, the model places it near the midpoint of its existence. According to Cornell University's summary of the research, the study centers on the cosmological constant, a term introduced by Albert Einstein in his theory of general relativity. In modern cosmology, the cosmological constant is commonly used to describe the simplest form of dark energy, the unknown phenomenon believed to be driving the accelerating expansion of the universe. "For the last 20 years, people believed that the cosmological constant is positive, and the universe will expand forever," Tye said in a Cornell University news release. "The new data seem to indicate that the cosmological constant is negative, and that the universe will end in a big crunch." The study draws on data from the Dark Energy Survey (DES) and the Dark Energy Spectroscopic Instrument (DESI), two major projects designed to investigate the nature of dark energy. According to Tye, recent observations suggest that dark energy may not behave exactly like a simple cosmological constant. To account for those observations, Tye and his collaborators proposed a model involving an extremely light hypothetical particle that evolves over time. In their calculations, this produces a negative cosmological constant and leads to a future collapse of the universe. The model predicts that cosmic expansion would continue for approximately another 11 billion years before reaching a maximum size, after which the universe would begin contracting and eventually collapse. Scientists have long debated how the universe might end. As explained in an article published in The Conversation by Stephen DiKerby of Michigan State University, several possibilities have been proposed. If dark energy remains constant and positive, the universe could continue expanding indefinitely, gradually becoming colder, darker and more diffuse in a scenario often called the "heat death" of the universe. Other theoretical possibilities include a Big Rip, in which cosmic expansion accelerates so dramatically that galaxies, stars and even atoms are torn apart, or a Big Crunch, in which expansion reverses and the universe collapses back into an extremely dense state. DiKerby notes that the Big Crunch idea itself is not new. What distinguishes Tye's work is that it attempts to use current observational data to estimate when such a collapse might occur and how it could unfold. Much of the universe's long-term evolution remains uncertain. According to current astrophysical understanding, stars will continue to form and die for billions of years. The Sun, for example, is about halfway through its expected lifespan. Galaxies are also expected to continue merging; the Milky Way and Andromeda galaxies are projected to collide several billion years from now. At the same time, the nature of dark energy remains one of the biggest unanswered questions in cosmology. While observations indicate that the universe's expansion is accelerating, scientists still do not know what is causing that acceleration. Future observations may therefore alter current predictions about the cosmos's ultimate fate. Tye emphasized that additional evidence will be needed before firm conclusions can be drawn. DESI continues to collect data, while upcoming observations from missions and observatories including Euclid, SPHEREx and the Vera C. Rubin Observatory are expected to provide more precise measurements of dark energy. "People have said before that if the cosmological constant is negative, then the universe will collapse eventually. That's not new," Tye said. "However, here the model tells you when the universe collapses and how it collapses." For now, the study presents one possible future for the cosmos rather than a settled prediction. Whether the universe ultimately ends in a Big Crunch, expands forever, or follows another path entirely remains an open question that future observations will help answer. Source: Cornell University, The Conversation This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
  • Recent Achievements

    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      570
    2. 2
      +Edouard
      175
    3. 3
      PsYcHoKiLLa
      73
    4. 4
      Michael Scrip
      68
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!